I use a weird 2.4GHz Remote for my MM, that reports itself as 3 input devices...
Two of them being a "keyboard" style device, one being a "accelerometer mouse"...whatever..

Anyhow, I wanted to accumulate the key presses from the two "keyboards" into my MM.

I thought it might be a simple approach to just encapsulate the evdev reading into a class and allow the config to have a comma separated eventPath value specifying more than one input source.

For example:
config: { evdev: { enabled: true, eventPath: "/dev/input/event0,/dev/input/event2", }, }

So i did that any quickly tested it.
All events end up being in the same socketNotification pipe, so the MM itself sees no source-distinction - which for me is fine.

I have basically not much knowledge about evdev and udev, so please correct me if that is nonsense..

I think it is a fancy addition to the module :)